Convert ISSUES.md into a GitHub issue form#32
Open
tas50 wants to merge 1 commit into
Open
Conversation
tas50
force-pushed
the
docs/issue-template
branch
from
June 28, 2026 05:18
3d4d21f to
db50194
Compare
Replace the static ISSUES.md instructions with a structured GitHub issue form so bug reports collect the needed details consistently. While converting, fix the stale `chefspec/chefspec` repo link, replace the deprecated `knife -v` with `chef --version`, drop the privacy-risky "paste everything from env" field, and add a missing ChefSpec version field. Signed-off-by: Tim Smith <tsmith84@proton.me>
tas50
force-pushed
the
docs/issue-template
branch
from
June 28, 2026 05:19
db50194 to
25ef76e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the static
ISSUES.mdfile with a structured GitHub issue form at.github/ISSUE_TEMPLATE/bug_report.yml, so new bug reports collect the information maintainers need (reproduction, versions, backtrace) in a consistent, guided way that renders in the GitHub "New issue" UI.Changes
.github/ISSUE_TEMPLATE/bug_report.yml— a guided bug-report form with required/optional fields and thebuglabel applied automatically.ISSUES.md— its purpose is now served by the form.While converting, I also corrected a few stale details carried over from
ISSUES.md:chefspec/chefspec→chef/chefspec.knife -vwithchef --versionfor capturing the Chef version.env" field (noisy and a potential vector for leaking secrets/credentials into a public issue).